SU bboards Guidelines 

SU BBoards is an electronic bulletin board system that interconnects
dozens of computers and hundreds of users at Stanford.  It is divided
into topical bboards, as listed just below.  A given message should go to
JUST ONE of these bboards.  In ambiguous cases, choose the closest fit and
post a pointer message on your second choice, e.g., "See my message about
<subject> on SU-<bboard>."

  SU-MARKET	- things for sale, "Where do I buy X?", comments on products,
		  merchants and service providers, e.g., "Who is a good
		  dentist?";
  SU-JOBS	- jobs wanted or offered;
  SU-EVENTS	- announcements of seminars, concerts and other events
		  inside and outside Stanford; ticket offers and requests
		  go to SU-MARKET;
  SU-COMPUTERS	- comments on computer services, "How do you do X on
		  system Y?"; discussion of SU-bboards policies; no ads for
		  computer products -- they go to SU-MARKET;
  SU-ETC	- everything else.

On SAIL, you can send mail directly to any of these bboards or to "CSD" (see
below).  When sending a message, please include a descriptive subject field
to aid people in selectively reading the bboard.

These bboards are available here as text files in the public bboard area
[BB,DOC] under the names MARKET.TXT, JOBS.TXT, EVENTS.TXT, COMPUT.TXT, and
ETC.TXT; CSD.TXT and a number of other bboards are also there.

These files can be read with E, and CKSUM can be used to locate things
that have changed in these files (READ CKSUM for more information).

SU-BBOARDS@SCORE.STANFORD.EDU is a valid address for messages from outside
Stanford.  Such messages will be manually screened and forwarded to the
appropriate list.

Local bboards that reach your intended audience should be used in preference to
SU-bboards.  Here are some important ones:
  CSD@Score	- Computer Science Department
  GSB@How	- Graduate School of Business
  BBOARD@Lear	- LOTS.
Such postings are automatically forwarded to bboards of the same name on
certain other machines within the same organization.

			    Protocols

In posting a message to one of these bboards, remember that it will be
seen by a large number of people.  In order to avoid wasting their time,
please use the following guidelines.

  BE CONCISE.  State your point, support it as needed, and stop.

  FORMAT your message with no more then 79 characters on a line --
  otherwise it will disappear off the edge of the screen on some systems.

  BE ACCURATE.  Check your message for accuracy and spelling before releasing
  it and be sure you send it to the right bboard.

  NO CORRECTIONS.  Do not send corrections to postings unless there is
  likelihood of serious misunderstanding.  Do not correct spelling errors
  but do feel embarrassed about them. If you posted to the wrong bboard,
  resend it to the correct one and be prepared to receive private complaints
  about the double posting.  Accept them gracefully.

  NO APOLOGIES.  If you make an error, do not post an apology.  Deal with
  any resulting problems privately.

In responding to postings by others, please do the following.

  USE PERSONAL MESSAGES unless you are reasonably sure that what you have
  to say will be of general interest to the bboard readers.

  BE POLITE even if the person you are responding to was not.  If you feel
  upset, wait until the feeling passes.  Reread the offending message to
  be sure that you are not misinterpreting it.  If you feel that you must
  use strong language, do so only in personal mail, not on the bboard.

  OVERLOOK MINOR ERRORS.  Remember that not everyone posting on the bboards
  is proficient in English and many can't spel wel.  If you see a consistent
  mispelling and wish to help avoid future embarrassment, send a private
  message.

If you:
 (a) receive a mailer error back from a message sent to one of the
     SU-bboards,
 (b) wish to call attention to an operating problem in these bboards, or
 (c) have comments on these guidelines,
you may send a message to SU-BB@Score.Stanford.EDU.

A copy of these guidelines will be reposted about once a month on
SU-COMPUTERS and should be retained on each participating system in a
"help" file.